Gas-filled aerial transport and methods of deploying unmanned aerial vehicles in delivering products

ABSTRACT

Described is an airborne fulfillment center (“AFC”) and the use of unmanned aerial vehicles (“UAV”) to deliver items from the AFC to users. For example, the AFC may be an airship that remains at a high altitude (e.g., 45,000 feet) and UAVs with ordered items may be deployed from the AFC to deliver ordered items to user designated delivery locations. As the UAVs descend, they can navigate horizontally toward a user specified delivery location using little to no power, other than to stabilize the UAV and/or guide the direction of descent. Shuttles (smaller airships) may be used to replenish the AFC with inventory, UAVs, supplies, fuel, etc. Likewise, the shuttles may be utilized to transport workers to and from the AFC.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.15/059,197, filed Mar. 2, 2016, entitled “Airborne Fulfillment CenterUtilizing Unmanned Aerial Vehicles For Item Delivery,” which is acontinuation of U.S. Pat. No. 9,305,280, filed Dec. 22, 2014, entitled“Airborne Fulfillment Center Utilizing Unmanned Aerial Vehicles For ItemDelivery” each of which is incorporated by reference herein in theirentirety.

BACKGROUND

Many companies package items and/or groups of items together for avariety of purposes, such as e-commerce and mail-order companies thatpackage items (e.g., books, CDs, apparel, food, etc.) to be shipped tofulfill orders from users. Retailers, wholesalers, and other productdistributors (which may collectively be referred to as distributors)typically maintain an inventory of various items that may be ordered byusers. A ground-based building, such as a materials handling facility,may maintain and process and ship such inventory.

Typically ordered items are packed in shipping packages (e.g.,corrugated boxes) and shipped to the user's residence or place ofbusiness. Physical delivery of items to user specified locations hasimproved dramatically over the years, with some retailers offering nextday delivery of ordered items. The final or last mile delivery ofphysical items to a user specified location is traditionallyaccomplished using a human controlled truck, bicycle, cart, etc. Forexample, a user may order an item for delivery to their home. The itemmay be picked from a ground-based materials handling facility, packedand shipped to the user for final delivery by a shipping carrier. Theshipping carrier will load the item onto a truck that is driven by ahuman to the final delivery location and the human driver, or anotherhuman companion with the driver, will retrieve the item from the truckand complete the delivery to the destination. For example, the human mayhand the item to a recipient, place the item on the user's porch, storethe item in a post office box, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical components or features.

FIG. 1 is a block diagram of a delivery environment that includes anairborne fulfillment center, according to an implementation.

FIG. 2 is a diagram of an unmanned aerial vehicle network, according toan implementation.

FIG. 3 is a diagram illustrating an unmanned aerial vehicle deliveryprocess that utilizes an airborne fulfillment center, according to animplementation.

FIG. 4 is an illustration of an airborne fulfillment center and ashuttle docked with the airborne fulfillment center, according to animplementation.

FIG. 5 is an illustration of a shuttle, according to an implementation.

FIG. 6 is an illustration of a top-down view of an unmanned aerialvehicle, according to an implementation.

FIG. 7 is another illustration of an unmanned aerial vehicle, accordingto an implementation.

FIG. 8 is a flow diagram of an example order delivery selection process,according to an implementation.

FIG. 9 is a flow diagram of an example unmanned aerial vehicle itemdelivery process, according to an implementation.

FIG. 10 is a flow diagram of an example airborne fulfillment centeradvertising and delivery process, according to an implementation.

FIG. 11 is a flow diagram of an example shuttle process, according to animplementation.

FIG. 12 is a block diagram of an example unmanned aerial vehicle controlsystem, according to an implementation.

FIG. 13 is a block diagram of an illustrative implementation of a serversystem that may be used with various implementations.

While implementations are described herein by way of example, thoseskilled in the art will recognize that the implementations are notlimited to the examples or drawings described. It should be understoodthat the drawings and detailed description thereto are not intended tolimit implementations to the particular form disclosed but, on thecontrary, the intention is to cover all modifications, equivalents andalternatives falling within the spirit and scope as defined by theappended claims. As used throughout this application, the word “may” isused in a permissive sense (i.e., meaning having the potential to),rather than the mandatory sense (i.e., meaning must). Similarly, thewords “include,” “including,” and “includes” mean including, but notlimited to. Additionally, as used herein, the term “coupled” may referto two or more components connected together, whether that connection ispermanent (e.g., welded) or temporary (e.g., bolted), direct or indirect(i.e., through an intermediary), mechanical, chemical, optical, orelectrical. Furthermore, as used herein, “horizontal” flight refers toflight traveling in a direction substantially parallel to the ground(i.e., sea level), and that “vertical” flight refers to flight travelingsubstantially radially outward from the earth's center. It should beunderstood by those having ordinary skill that trajectories may includecomponents of both “horizontal” and “vertical” flight vectors.

DETAILED DESCRIPTION

This disclosure describes systems and methods for utilizing an aerialfulfillment center (“AFC”) and unmanned aerial vehicles (“UAV”) tofacilitate delivery of ordered items to users. An AFC may be afulfillment center that is supported by and/or incorporated into anairship. An airship, or dirigible, is a type of aerostat orlighter-than-air aircraft which can navigate through the air under itsown power. Airships gain their lift from gas that is less dense than thesurrounding air, such as helium or hot air.

An AFC may be positioned at an altitude above a metropolitan area and bedesigned to maintain an inventory of items that may be purchased by auser and delivered to the user by a UAV that is deployed from the AFC.For example, a user may browse an e-commerce website and place an orderfor an item that is in the inventory of the AFC. Upon placing the orderfor the item, fulfillment instructions may be sent to the AFC and a UAVwithin the AFC may engage the item for delivery to the user. When theUAV departs the AFC, it may descend from the high altitude of the AFCusing little or no power other than to guide the UAV towards itsdelivery destination and/or to stabilize the UAV as it descends.

When the UAV approaches earth, the UAV may engage the motors of the UAVand utilize the lifting forces generated by the motors and correspondingpropellers of the UAV to slow the descent of the UAV and to completenavigation to the user specified delivery location. When the UAV reachesthe delivery location, it may disengage the ordered item and completethe delivery.

After completing an item delivery, the UAV may navigate to a nearbyground based materials handling facility or a shuttle replenishmentlocation. Because of the high altitude of the AFC, navigation by a UAVback to the AFC may not be feasible, or an efficient use of power.Accordingly, a replenishment shuttle may be provided at a shuttlereplenishment location that is configured to transport inbound items(e.g., UAVs, inventory, workers, supplies, fuel) to the AFC and retrieveoutbound items (e.g., overstock inventory, transshipments, workers,waste) from the AFC. For example, the replenishment shuttle may beanother, smaller, airship that is used to transport items to and fromthe AFC.

By utilizing an AFC for the storage and delivery of items using UAVs,the power required to complete an item delivery is substantiallyreduced. Rather than the UAV having to operate at power from the time itdeparts the materials handling facility to the delivery location andback to the materials handling facility (or another location), the UAVmay be deployed from the AFC and descend under the forces of gravitytoward a delivery location using little to no power. Only as the UAVapproaches earth does it need to fully engage the UAV motors to maintainflight and complete delivery of the item.

The use of an AFC and shuttles also provides another benefit in that theAFC can remain airborne for extended periods of time. In addition,because the AFC is airborne, it is not limited to a fixed location likea traditional ground based materials handling facility. In contrast, itcan navigate to different areas depending on a variety of factors, suchas weather, expected demand, and/or actual demand.

An AFC may navigate to an area based on various positioning factors. Forexample, a temporal event (e.g., a football game) may be expected toproduce a demand for certain types of items (e.g., sportingparaphernalia, food products, etc.). In advance of the event, the itemsmay be delivered to the AFC in a quantity sufficient to satisfy theexpected demand and the AFC may navigate to a position such that UAVsdeployed from the AFC can safely navigate to the location of the eventand deliver the items, thereby satisfying the demand. In someimplementations, the AFC may navigate to a lower altitude and provideadvertising for the temporal event or for other occasions (e.g., productannouncements, product releases, sales).

As still another benefit, items may be delivered within minutes of auser placing an order. For example, a user may place an order fordelivery of item A, which is maintained in the inventory of an AFCwithin a defined distance from the user. Item A may be picked frominventory, engaged by a UAV and the UAV may be deployed from the AFC.The picking of item A through deployment may be completed within minutesof the user's order. In some implementations, some UAVs may bepre-engaged with inventory items so that when an order for such an itemis received, a UAV with the engaged inventory can be immediatelydeployed, further reducing the delivery time.

Deployed UAVs may quickly descend toward a user specified deliverylocation (e.g., the location of the user) and deliver the item. Thisspeed of delivery provides near instant gratification to users for itempurchases and greatly increases the breadth of items that can bedelivered. For example, perishable items or even prepared meals can bedelivered in a timely fashion to a user. In general, any item that canbe carried by a UAV may be delivered using the implementations discussedherein.

An inventory management system may be configured to communicate (e.g.,wirelessly) with the AFC, shuttle(s), and/or UAVs. In variousimplementations, the general activities of the AFC, shuttles(s) and/orUAVs (e.g., related to the delivery of items, the replenishment ofinventory and/or UAVs to the AFC, the travel of UAVs to and from thedesignated delivery locations, etc.) may be coordinated by the inventorymanagement system. For example, the inventory management system mayreceive or determine schedule data for the travel of the shuttles to andfrom the AFC. In various implementations, the inventory managementsystem may also receive tracking data (e.g., GPS) regarding thelocations of the AFCs, shuttles and/or UAVs and use that data forvarious purposes (e.g., status monitoring, answering location statusrequests, sending notifications regarding the current location of theAFCs, shuttles, UAVs).

FIG. 1 is a block diagram of a delivery environment 100 that includes anAFC 102, according to an implementation. As will be described in moredetail below, an AFC 102 may be utilized to store inventory items andfacilitate UAV delivery of ordered items to users.

The delivery environment 100 includes a user interface that allows auser 104 to place an order for an item that is to be delivered to theuser. The user interface may be a graphical user interface, an audioonly interface, a multi-mode interface, or any other interface forinteracting with the user 104. The user interface may be provided to theuser 104 through any type of electronic device 106, such as a tablet,desktop, laptop, smart phone, personal digital assistant, netbook, etc.The user interface may be delivered to the electronic device 106 by oneor more remote computing resources 110 that make up part or all of anelectronic-commerce shopping environment. In other implementations, theuser interface may provide a direct communication between a user and anagent.

The remote computing resources 110 may form a portion of anetwork-accessible computing platform implemented as a computinginfrastructure of processors, storage, software, data access, and othercomponents that is maintained and accessible via a network. Services,such as e-commerce shopping services, offered by the remote computingresources 110 do not require that the user have knowledge of thephysical location and configuration of the system that delivers theservices. The electronic device 106 may communicatively couple to theremote computing resources 110 via the network which may represent wiredtechnologies (e.g., wires, USB, fiber optic cable, etc.), wirelesstechnologies (e.g., RF, cellular, satellite, Bluetooth, etc.), and/orother connection technologies. The network carries data between theelectronic device 106 and the remote computing resources 110.

After receiving from a user 104 an order for an item that may betransported by a UAV 112 from an AFC 102 and delivered to a userspecified delivery location, the electronic device 106 may send thisinformation to the remote computing resources 110 over the network. Asillustrated, the remote computing resources 110 may include one or moreservers, such as servers 120(1), 120(2), . . . , 120(N). These servers120(1)-(N) may be arranged in any number of ways, such as server farms,stacks, and the like that are commonly used in data centers.Furthermore, the servers 120(1)-(N) may include one or more processors122 and memory 124 that may store an inventory management system 126.

The inventory management system 126 may be configured, for example, toperform order planning and filling of materials handling facility 130,to perform order planning, replenishment for AFCs 102 and/or to performorder planning and fulfillment of orders by UAVs 112 and/or bytraditional delivery mechanism (e.g., vehicles). In variousimplementations, one or more AFCs 102 may be configured to generallyperform some or all of the functions that are traditionally done by aground-based materials handling facility 130, except they are airborne.

A shuttle 150 may be used to replenish the AFC 102. For example, as UAVs112 are deployed from an AFC 102 to deliver ordered items to a user 104,the AFC is depleted of both inventory and UAVs. The inventory managementsystem 126 may instruct UAVs, after completing a delivery, to navigateto a shuttle positioned at a replenishment area. The shuttles 150 may beloaded with UAVs, inventory, workers, materials handling equipment,and/or other inbound items and navigate to the AFC 102 to replenish theAFC 102. Likewise, a shuttle, after offloading the inbound items at theAFC 102, may receive outbound items (e.g., overstocked items,transshipment items, workers, materials handling equipment, waste) fromthe AFC 102 and transport those items back to a ground based materialshandling facility 130 and/or to another location.

The AFC 102, UAVs 112 and/or the shuttles 150 may communicatively coupleto the remote computing resources 110 via a network. For example, thecommunications to and from the AFC 102, shuttles 150 and/or UAVs 112 mayutilize wireless antennas of the AFC 102, shuttles 150 and/or UAVs 112.

In various implementations, the inventory management system 126 and/orAFC 102 may send instructions to or otherwise control the UAVs 112 fordelivering items, navigating to shuttles, navigating to materialshandling facilities 130, and the like. As discussed further below withrespect to FIGS. 2-3, UAVs 112 that are operating at lower altitudes mayform a UAV network 200, alone or in combination with the inventorymanagement system 126, landed shuttles 150 and/or ground based materialshandling facilities 130. In some implementations, the UAV network 200may also include the AFC 102, airborne shuttles 150 and/or UAVsdescending from higher altitudes.

In various implementations, the remote computing resources 110 and/orinventory management system 126 may also receive tracking data (e.g.,GPS) regarding the coordinates of the UAVs 112, shuttles 150 and/or AFCs102. The GPS data may be utilized for various purposes, such asanswering location status requests or for sending notificationsregarding the current locations of the AFCs and/or UAVs. For example, auser may request that a notification be sent when an UAV 112 with anitem ordered by the user has departed the AFC and/or is approaching. Asanother example, a notification may be sent to a UAV that has completedan item delivery identifying a location of a shuttle 150 to which theUAV 112 is to navigate. Notifications may also be sent from the AFC 102,shuttles 150 and/or UAVs 112 to the remote computing resources 110and/or inventory management system 126 regarding various events (e.g.,when a UAV has been deployed from an AFC, when a shuttle has reachedcapacity, when an AFC is running low on inventory and/or UAVs).

FIG. 2 depicts a block diagram of a UAV network 200 that includes UAVs212, delivery locations 203, shuttle replenishment locations 251,materials handling facilities 230 and an inventory management system226, according to an implementation.

Each of the UAVs 212, delivery locations 203, shuttle replenishmentlocations 251, materials handling facilities 230 and/or inventorymanagement system 226 may be configured to communicate with one another.For example, the UAVs 212 may be configured to form a wireless network200 that utilizes Wi-Fi or another wireless means of communication, eachUAV communicating with other UAVs within wireless range. In otherimplementations, the UAVs 212, inventory management system 226,materials handling facilities 230, shuttle replenishment locations 251and/or the delivery locations 203 may utilize existing wireless networks(e.g., cellular, Wi-Fi, satellite) to facilitate communication. In someimplementations, one or more of the inventory management system 226,materials handling facilities 230, delivery locations 203 and/or shuttlereplenishment locations 251 may also communicate with each other viaanother network (wired and/or wireless), such as the Internet. Likewise,a shuttle (not shown) and/or an AFC (not shown) may communicate withand/or be part of the wireless network 200.

As discussed above, the inventory management system 226 may beconfigured to communicate with the delivery locations 203, UAVs 212,materials handling facilities 230, AFCs, shuttles, and/or shuttlereplenishment locations 251. As an example, position information foreach UAV 212 may be determined and shared among UAVs. Each UAV mayperiodically transmit, for example, ADS-B information to other UAVs inthe network. When information, such as ADS-B information, is sent to orfrom a UAV, the information may include an identifier for the UAV andeach UAV may act as a node within the network, forwarding theinformation until it is received by the intended UAV. For example, theinventory management system 226 may send a message to UAV 212-6 bytransmitting the information and the identifier of the intendedreceiving UAV to one or more of UAVs 212-1, 212-2, 212-3 that are inwireless communication with the inventory management system 226. Eachreceiving UAV will process the identifier to determine if it is theintended recipient and then forward the information to one or more otherUAVs that are in communication with the UAV. For example, UAV 212-2 mayforward the message and the identification of the intended receiving UAVto UAV 212-1, 212-3 and 212-5. In such an example, because UAVs 212-1,212-3 have already received and forwarded the message, it may discardthe message without forwarding it again, thereby reducing load on thenetwork 200. The other UAVs, upon receiving the message, may determinethat they are not the intended recipient and forward it on to othernodes. This process may continue until the message reaches the intendedrecipient.

In some implementations, if a UAV loses communication with other UAVsvia the wireless network 200, it may activate another wirelesscommunication path to regain connection. For example, if a UAV 212cannot communicate with any other UAVs via the network 200, it mayactivate a cellular and/or satellite communication path to obtaincommunication information from the inventory management system 226,materials handling facility 230, shuttle replenishment location 251and/or a delivery location 203. If the UAV still cannot regaincommunication and/or if it does not include an alternative communicationcomponent, it may automatically and autonomously navigate toward adesignated location (e.g., a nearby materials handling facility 230,shuttle replenishment location 251 and/or delivery location 203).

The wireless mesh network 200 may be used to provide communicationbetween UAVs (e.g., to share weather information including wind speedsand directions, location information, routing information, landingareas), the inventory management system 226, materials handlingfacilities 230, delivery locations 203 and/or shuttle replenishmentlocations 251.

In addition, in some implementations, the wireless network 200 may beused to deliver content and/or other information to other computingresources, such as personal computers, electronic book reading devices,audio players, mobile telephones, tablets, desktops, laptops, etc. Forexample, the mesh network may be used to deliver electronic book contentto electronic book reading devices of users.

FIG. 3 is a block diagram illustrating an unmanned aerial vehicledelivery process that utilizes an airborne fulfillment center 302,according to an implementation. As illustrated, an AFC 302 may bepositioned above a metropolitan area 304 at a high altitude (referred toherein as a fulfillment center altitude). For example, the AFC 302 maybe positioned at an altitude of 45,000 feet or more above themetropolitan area 304. Positioning the AFCs 302 at an altitude above45,000 takes them out of the flight path of commercial airplanes, whichgenerally have a maximum usable altitude of approximately 42,000 feet.Because the AFCs 302 are not in the flight path of other aerialvehicles, they can remain at a position for extended periods of timewithout disrupting other aerial systems. Likewise, by placing the AFC302 at a fulfillment center altitude, the area that can be serviced byUAVs 312 deployed from the AFC 302 to deliver items is increased. Forexample, UAVs deployed from the AFC 302 may travel horizontally as theydescend, thereby expanding the coverage area of the AFC 302. In someimplementations, the UAVs 312 may include a wing or other airfoil, asillustrated in FIG. 7, thereby further extending their ability to travelhorizontally during descent without requiring much or any powerconsumption.

As orders are placed by users in the metropolitan area 304 for itemsthat are included in the inventory of the AFC 302, the item is engagedby a UAV 312 and the UAV 312 is deployed from the AFC 302. As the UAV312 descends, it may navigate toward the user specified deliverylocation using wings and/or propellers of the UAV 312. For example, ifthe UAV 312 includes a wing, it may glide down from the AFC 302 andnavigate toward the delivery location using the ailerons of the wing tocontrol the direction of the descent. Likewise, the propellers of theUAV may be allowed to freely rotate from the forces of wind passing overthe propellers during the descent. The rotation of the propellers mayact as generators to provide any additional charging needed for thepower modules of the UAV 312.

If the UAV 312 does not include a wing, such as the UAV discussed belowwith respect to FIG. 6, it may still navigate horizontally by engagingand/or disengaging different motors and corresponding propellers of theUAV 312 to control the direction and speed of the descent of the UAV312.

As a result of the guided descent, and potential power generation, theUAV 312 can travel a large distance and be near the delivery locationbefore it must use the motors and propellers to maintain flight, therebyconserving power over the duration of the delivery.

As the UAV 312 enters the UAV network 300, the UAV 312 communicates withother UAVs 312. Likewise, the UAV 312 may engage the motors andcorresponding propellers to slow the descent of the UAV 312 and completethe navigation of the UAV 312 to the user specified delivery locationwithin the metropolitan area 304 and deliver the item.

Upon completion of item delivery, the UAV 312 may navigate to a shuttlereplenishment location 351 that includes a shuttle 350, to a materialshandling facility 330, which may also include a shuttle replenishmentlocation, and/or to another location. UAVs 312 deployed from an AFC 302may be instructed to return to the AFC 302 via a shuttle or may beincorporated into the UAV network 300 to deliver items from a materialshandling facility or other location. Likewise, UAVs 312 that are part ofthe UAV network 300 may be instructed to load onto a shuttle 350 and beprovided to the AFC 302 for deployment.

As illustrated, one or more shuttles 350 may be used to replenish theAFC 302, thereby extending the duration of flight of the AFC 302. Forexample, shuttles 350 may deliver inbound items, discussed below, to theAFC 302. Like the AFCs 302, the shuttles 350 may be airships and mayascend from earth and navigate to and dock with the AFC 302 withoutconsuming large amounts of power. The shuttles 350 may be smaller thanthe AFC 302 and configured to make multiple trips to and from the AFC302 providing inbound items to the AFC and retrieving outbound itemsfrom the AFC 302.

In some implementations, multiple AFCs 302 may be positioned ataltitudes to provide coverage for a larger area. Shuttles within thelarger area may provide inbound items to any of the AFCs 302, retrieveoutbound items from the AFCs 302 and/or navigate between the AFCs 302.Accordingly, some shuttles 350 may be used to provide inbound itemsand/or retrieve outbound items from multiple AFCs 302 and/or to provideitems between AFCs. In some implementations, shuttles may navigatebetween AFCs, transshipping items, without returning to earth. In suchan implementation, the shuttle 350 may receive fuel and/or service whiledocked at one of the AFCs 302.

In operation, when an order for one or more items is placed by a user,the order is assigned for fulfillment. The inventory management systemmay determine if there is an AFC 302 within a delivery range of the userspecified delivery location for the order and whether that AFC includesthe ordered items. If an AFC is within range and has the inventory, theorder may be associated with the AFC for delivery. If the inventory isnot available at an AFC within range of the delivery location, the itemmay be transported to an AFC for delivery or delivered directly from aground-based materials handling facility.

In some implementations, the AFC 302 may navigate to a lower altitude(e.g., 2,000 feet above the metropolitan area 304) to provideadvertising, decrease the delivery time and/or to satisfy an expecteddemand (e.g., at a temporal event). For example, the exterior of the AFC302 may include one or more output devices (e.g., visual, audible) thatcan be used to present advertising or other information about itemsand/or services. For example, if 100 units of Item A are offered forsale for delivery from the AFC 302, the AFC 302 may navigate to a loweraltitude (referred to herein as an advertising altitude) and present anadvertisement regarding the sale and the number of units remaining. Auser may place an order for the item (Item A), the item is picked frominventory, engaged by a UAV 312 and deployed for delivery. In someimplementations, to further increase the speed at which items aredelivered as part of a sale, the quantity offered for sale may bepre-engaged by UAVs and as soon as the item is ordered, a UAV with theitem may be deployed for delivery.

Once an item is ordered and delivery is initiated, the output device ofthe AFC may be updated to illustrate a decrement in item count for itemsremaining to be sold at the advertised sale price. At the advertisingaltitude, the user may be able to see the UAV as it is deployed and asit delivers the item to the designated location. In someimplementations, the UAV may include a flashing light, smoke or othervisual identifier to aid in the identification of the UAV by the user asthe item is delivered.

As another example, the AFC 302 may navigate to an advertising altitudeso that an expected demand or a known demand for a product can besatisfied. For example, if an event is scheduled to occur at a stadium(temporal event), the items likely to be ordered are determined andstocked in the inventory of the AFC 302. In advance of the event, theAFC 302 may navigate to a position near the event and advertise thestocked inventory items for delivery using a UAV that is deployed fromthe AFC 302. Ordered items can be delivered from the AFC 302 in minutes.

As still another example, ordered items (e.g., pre-release items) may bestocked in the AFC 302 and the AFC may navigate to an area that has ahigh demand for the items and provide delivery of those items to thecustomers that ordered the items when the items are released.

FIG. 4 is an illustration of an AFC 402 and a shuttle 450 docked withthe AFC 402, according to an implementation. As illustrated, the AFC 402may be configured as an airship. An airship is a type of aerostat orlighter-than-air aircraft that can navigate through the air under itsown power. The AFC 402 includes a lifting portion 404, which includesthe lighter than air gas, and a fulfillment center 406 which is used tostore inventory, deploy UAVS, etc. The fulfillment center may be coupledwith the lifting portion using a variety of techniques. For example, asillustrated, the fulfillment center 406 may be suspended using cablesfrom the lifting portion 404 of the AFC 402. In other implementations,the fulfillment center 406 may be directly mounted to or incorporatedwith the lifting portion 404.

The fulfillment center 406 of the AFC 402 may include one or more UAVdeployment bays 408 and one or more docking bays 412 or docking arms414. Depending on the configuration of the shuttle 450 and/or the AFC402, the docking bay 412 and/or docking arm 414 may be utilized. Forexample, as illustrated, the docking arm 414 has been extended from theAFC 402 and docked or mated to the shuttle 450 to facilitate thetransfer of inbound items and outbound items between the AFC 402 and theshuttle 450. As another example, if the lifting portion of the AFC 402has a toroid shape, the shuttle 450 may navigate through the opening ofthe toroid and dock with the top of the fulfillment center 406 of theAFC 402.

The airship that is utilized for the AFC 402 may be any type of airship.For example, the airship may be a non-rigid airship, a semi-rigidairship, or a rigid airship. Likewise, the AFC 402 may be of any size,shape and/or configuration. In some implementations, the AFC may behundreds of feet long and capable of carrying several hundreds of tons.In other implementations, the airship may have the shape of a toroid, atubular shape, a spherical shape, include multiple portions, etc.

The control of the AFC 402 may be manual (e.g., a pilot) or automated(e.g., directly or remotely controlled by an automated system, robotic,etc.). The AFC 402 may likewise include one or more internal computingsystems (not shown), that are capable of maintaining system informationfor the AFC 402 and/or providing other computing functions. For example,the internal computing system may include an inventory component thatmaintains current inventory level information, where inventory islocated in the AFC, and the like. The AFC 402 may be configured toobtain information from a remote computing resource and/or the inventorymanagement system.

Likewise, the fulfillment center 406 of the AFC may be operated by humanworkers, automated with robotic equipment, such as Kiva System® mobiledrive units, or a combination thereof. When the AFC is occupied byhumans, it may be pressurized and temperature controlled. Likewise,radiation shielding may be utilized to protect workers from exposure dueto the location of the AFC.

The fulfillment center 406 may utilize any variety of materials handlingequipment. Materials handling equipment includes, but is not limited tomobile drive units, forklifts, shelving, bins, totes, carts, boxes,trolleys, containers, tape, labels, printers, packing supplies, and thelike.

FIG. 5 is an illustration of a replenishment shuttle 550, according toan implementation. As illustrated, the shuttle 550, like the AFC 402(FIG. 4), may be configured as an airship. The airship that is utilizedfor the shuttle 550 may be any type of airship. For example, the airshipmay be a non-rigid airship, a semi-rigid airship, or a rigid airship.Likewise, the shuttle 550 may be of any size and/or configuration. Insome implementations, the shuttle 550 may be one hundred feet long.

The control of the shuttle 550 may be manual (e.g., a pilot) orautomated (e.g., directly or remotely controlled by an automated system,robotic, etc.). The shuttle 550 may likewise include one or moreinternal computing systems (not shown), that are capable of maintainingsystem information for the shuttle 550 and/or providing other computingfunctions.

As illustrated in the expanded view 502, the shuttle 550 may beconfigured to transport inbound items to an AFC. Inbound items may beany items that are to be delivered to an AFC. For example, inbound itemsmay include UAVs 512, inventory 504, workers, supplies, fuel, materialshandling equipment, etc. Different types of inbound items may betransported on the same or different shuttles 550. For example, theshuttle 550 illustrates that both inventory items 504 and UAVs 512 maybe transported by the shuttle 550 to an AFC. In some implementations,the shuttle 550 may be configured to provide charging to the UAVs 512 asthey are being transported to the AFC so the UAVs 512 are at or near afull charge and ready for deployment when the UAVs arrive at the AFC.

In some implementations, one or more of the UAVs 512 may be positionedon an external portion of the shuttle 550 and be pre-loaded withinventory (such as high volume inventory, or currently orderedinventory). If an order of an item that is pre-loaded on a UAVpositioned on an external portion of the shuttle 550 is received, theUAV may be deployed from the shuttle 550 as the shuttle is in transit toor from the AFC. Likewise, if a UAV positioned on the outside of theshuttle 550 is carrying an item that has already been ordered, the UAVmay deploy from the shuttle 550 once the shuttle reaches an altitudethat allows the UAV to navigate to the delivery location for the ordereditem using reduced or no power.

The shuttle may also be used for advertising. For example, as theshuttle is navigating to or from an AFC, the shuttle may presentadvertisements using an output device (e.g., display, audio, etc.) ofthe shuttle. The advertisement may be for an item available for deliveryfrom the AFC, an item available for immediate delivery by a UAV mountedto the shuttle, an advertisement for a service, etc.

Inventory items that are transported by a shuttle to an AFC may includeitems corresponding to an existing user order, high-volume items,release day items, sale items, and/or other items expected to be indemand within a delivery range of the AFC. A high-volume item may be,for example, an item that is frequently ordered, such as a popular book,shoe, video game, tablet, etc. A release day item may be an item thatwill become available for delivery on the day it is released to thepublic (e.g., book, movie, game, toy, etc.).

In addition to providing inbound items to an AFC, the shuttle mayreceive outbound items from the AFC. Outbound items include any itemsthat are to be removed from the AFC. For example, outbound items mayinclude overstock items, transshipment items, waste, damaged items,workers, etc. In some implementations, one or more UAVs may also beutilized to transport outbound items from an AFC.

While the examples discussed herein describe an AFC and a shuttle thatare configured to include an airship, it will be appreciated that othertypes of aerial vehicles may be utilized, for either or both of the AFCand/or the shuttle, with the implementations described herein.

FIG. 6 illustrates a block diagram of a top-down view of a UAV 612according to an implementation. As illustrated, the UAV 612 includeseight lifting propellers 602-1, 602-2, 602-3, 602-4, 602-5, 602-6,602-7, 602-8 spaced about the frame 604 of the UAV. The liftingpropellers 602 may be any form of propeller (e.g., graphite, carbonfiber) and of a size sufficient to lift the UAV 612 and any item engagedby the UAV 612 so that the UAV 612 can navigate through the air, forexample, to deliver an item. While this example includes eight liftingpropellers, in other implementations, more or fewer propellers may beutilized. Likewise, in some implementations, the lifting propellers maybe positioned at different locations on the UAV 612. In addition,alternative methods of propulsion may be utilized. For example, fans,jets, turbojets, turbo fans, jet engines, and the like may be used topropel the UAV.

The frame 604 or body of the UAV 612 may likewise be of any suitablematerial, such as graphite, carbon fiber, and/or aluminum. In thisexample, the frame 604 of the UAV 612 includes four rigid members 605-1,605-2, 605-3, 605-4, or beams arranged in a hash pattern with the rigidmembers intersecting and joined at approximately perpendicular angles.In this example, rigid members 605-1 and 605-3 are arranged parallel toone another and are approximately the same length. Rigid members 605-2and 605-4 are arranged parallel to one another, yet perpendicular torigid members 605-1 and 605-3. Rigid members 605-2 and 605-4 areapproximately the same length. In some embodiments, all of the rigidmembers 605 may be of approximately the same length, while in otherimplementations some or all of the rigid members may be of differentlengths. Likewise, the spacing between the two sets of rigid members maybe approximately the same or different.

While the implementation illustrated in FIG. 6 includes four rigidmembers 605 that are joined to form the frame 604, in otherimplementations, there may be fewer or more components to the frame 604.For example, rather than four rigid members, in other implementations,the frame 604 of the UAV 612 may be configured to include six rigidmembers. In such an example, two of the rigid members 605-2, 605-4 maybe positioned parallel to one another. Rigid members 605-1, 605-3 andtwo additional rigid members on either side of rigid members 605-1,605-3 may all be positioned parallel to one another and perpendicular torigid members 605-2, 605-4. With additional rigid members, additionalcavities with rigid members on all four sides may be formed by the frame604. As discussed further below, a cavity within the frame 604 may beconfigured to include an item engagement mechanism for the engagement,transport, and delivery of item(s) and/or containers that containitem(s).

In some implementations, the UAV may be configured for aerodynamics. Forexample, an aerodynamic housing may be included on the UAV that enclosesthe UAV control system 610, one or more of the rigid members 605, theframe 604, and/or other components of the UAV 612. The housing may bemade of any suitable material(s) such as graphite, carbon fiber,aluminum, etc. Likewise, in some implementations, the location and/orthe shape of the item engagement mechanism and/or any items orcontainers may be aerodynamically designed.

In some instances, a container may be utilized for holding an item,wherein the item engagement mechanism engages the item by engaging thecontainer. For example, specially shaped containers for use with the UAV612 may be aerodynamically designed and provided in the AFC, such that aworker or automated system is able to select one of the containers andplace the item in the container for engagement by the UAV 612.

The containers may be configured to account for the change in pressureas the UAV descends from the AFC. For example, the container may be arigid body with one or more openings or baffles that allow pressure toequalize between the interior of the container and the atmosphere aroundthe container. Likewise, the containers may have thermal characteristicsto keep items within the containers at a desired temperature. Forexample, if prepared hot food is being delivered, the container may bedesigned to keep the food at a desired temperature until the food isdelivered to the user.

In some implementations, the item engagement mechanism may be configuredsuch that, when an item and/or container is engaged, it is enclosedwithin the frame and/or housing of the UAV 612 so that no additionaldrag is created during transport of the item. In other implementations,the item and/or container may be shaped to reduce drag and provide amore aerodynamic design. For example, if a portion of a containerextends below the UAV when engaged, the exposed portion of the containermay have a curved shape.

The lifting propellers 602 and corresponding lifting motors arepositioned at both ends of each rigid member 605. The lifting motors maybe any form of motor capable of generating enough speed with the liftingpropellers to lift the UAV 612 and any engaged item thereby enablingaerial transport of the item. For example, the lifting motors may eachbe a FX-4006-13 740 kv multi rotor motor.

Extending outward from each rigid member is a support arm 606 that isconnected to a safety barrier 608. In this example, the safety barrieris positioned around and attached to the UAV 612 in such a manner thatthe motors and propellers 602 are within the perimeter of the safetybarrier 608. The safety barrier may be plastic, rubber, etc. Likewise,depending on the length of the support arms 606 and/or the length,number or positioning of the rigid members 605, the safety barrier maybe round, oval, or any other shape.

Mounted to the frame 604 is the UAV control system 610. In this example,the UAV control system 610 is mounted in the middle and on top of theframe 604. The UAV control system 610, as discussed in further detailbelow with respect to FIG. 12, controls the operation, routing,navigation, communication, and the item engagement mechanism of the UAV612.

The UAV 612 also includes one or more power modules 613. In thisexample, the UAV 612 includes two power modules 613 that are removablymounted to the frame 604. The power module for the UAV may be in theform of battery power, solar power, gas power, super capacitor, fuelcell, alternative power generation source, or a combination thereof. Forexample, the power modules 613 may each be a 6000 mAh lithium-ionpolymer battery, polymer lithium ion (Li-poly, Li-Pol, LiPo, LIP, PLI,or Lip) battery. The power module(s) 613 are coupled to and providepower for the UAV control system 610 and the propeller motors. In someimplementations, one or more of the power modules may be configured suchthat it can be autonomously removed and/or replaced with another powermodule while the UAV is landed (e.g., such power modules may be providedor replaced while the UAV is landed in a shuttle). In someimplementations, when the UAV is within a shuttle or mounted to anexterior of a shuttle, the UAV may engage with a charging member torecharge the power module. In some implementations, when the UAV isdescending from the AFC, it may utilize the propellers and correspondingmotors as generators to further charge the power modules 613.

As mentioned above, the UAV 612 may also include an item engagementmechanism 614. The item engagement mechanism may be configured to engageand disengage items and/or containers that hold items. In this example,the item engagement mechanism 614 is positioned within a cavity of theframe 604 that is formed by the intersections of the rigid members 605.The item engagement mechanism may be positioned beneath the UAV controlsystem 610. In implementations with additional rigid members, the UAVmay include additional item engagement mechanisms and/or the itemengagement mechanism 614 may be positioned in a different cavity withinthe frame 604. The item engagement mechanism 614 may be of any sizesufficient to securely engage and disengage items and/or containers thatcontain items. In other implementations, the engagement mechanism mayoperate as the container, containing the item(s) to be delivered. Theitem engagement mechanism communicates with (via wired or wirelesscommunication) and is controlled by the UAV control system 610.

As will be described in more detail below with respect to FIG. 12, theUAV control system 610 may operate in conjunction with or may otherwiseutilize or communicate (e.g., via wired and/or wireless communication)with one or more components of the inventory management system 126,shuttles, and/or the AFC. Likewise, components of the inventorymanagement system 126, shuttles, and/or the AFC may generally interactand communicate with the UAV control system 610.

While the implementations of the UAV discussed herein utilize liftingpropellers to achieve and maintain flight, in other implementations, theUAV may be configured in other manners. In one implementation, the UAVmay include fixed wings and/or a combination of both propellers andfixed wings, as illustrated in FIG. 7.

FIG. 7 depicts another view of a UAV 712, according to animplementation. In the example illustrated in FIG. 7, the UAV 712includes a wing 718 coupled to the frame 704 of the UAV 712. The wing718 may be formed of any suitable material such as, but not limited to,carbon fiber, aluminum, fabric, plastic, fiberglass, wood, etc. The wing718 may be coupled to the top of the frame 704 and positioned above athrusting motor housing 720 that includes the thrusting motor andthrusting propeller.

The thrusting motor housing 720 may be aerodynamically shaped andconfigured to encase a thrusting motor and/or a thrusting propeller. Thethrusting motor and the thrusting propeller may be the same or differentthan the lifting motors and lifting propellers 702. For example, in someimplementations, the thrusting motor may be a Tiger U-8 motor and thethrusting propeller may have a dimension of eighteen inches. In otherimplementations, the thrusting motor and thrusting propeller may beformed with the thrusting motor housing 720 as a single unit, such as aducted fan system. In some implementations, the thrusting propeller mayhave a smaller dimension than the lifting propellers 702. In otherimplementations, the thrusting motors may utilize other forms ofpropulsion to propel the UAV. For example, fans, jets, turbojets, turbofans, jet engines, internal combustion engines, and the like may be used(either with propellers or with other devices) as the thrusting motors.

The thrusting motors and thrusting propellers may be oriented atapproximately ninety degrees with respect to the lifting propellers 702and utilized to increase the efficiency of flight that includes ahorizontal component. For example, when the UAV 712 is traveling in adirection that includes a horizontal component, the thrusting motors maybe engaged to provide horizontal thrust force via the thrustingpropellers to propel the UAV 712 horizontally. As a result, the speedand power utilized by the lifting motors may be reduced. Alternatively,in selected implementations, the thrusting motor may be oriented at anangle greater or less than ninety degrees with respect to the liftingpropellers 702 to provide a combination of pushing and lifting thrust.

The wing 718 is designed to have an airfoil shape to provide lift to theUAV 712 as the UAV 712 moves horizontally. In some implementations,utilizing the thrusting motors and the thrusting propellers inconjunction with the wing 718, or just the wing, when the UAV 712 isdescending from the AFC, the UAV may travel long horizontal distances(miles) from the AFC using little to no power. In implementations wherethe wing 718 includes flaps and/or ailerons, the pitch, yaw and roll ofthe UAV 712 may be controlled using the flaps and/or ailerons alone orin combination with the lifting motors and lifting propellers 702 and/orthe thrusting motors and thrusting propellers. If the wing 718 does notinclude flaps and/or ailerons, the lifting motors and lifting propellers702 and/or the thrusting motors and thrusting propellers may be utilizedto control the pitch, yaw, and/or roll of the UAV 712 during flight. Insome implementations, the wing 718 may be configured to rotate or pivotabout the frame 704 of the UAV 712 to reduce or increase drag when theUAV 712 is moving in a direction that includes a vertical component.

The UAV 712 may be configured with eight lifting propellers 718 and oneor more thrusting motors and thrusting propellers, as shown, or may havea different configuration. In another configuration, the wing may bemounted to a UAV that includes eight lifting motors and correspondinglifting propellers but no thrusting motors or thrusting propellers, suchas the UAV 612 (FIG. 6). In still another example, the UAV may have fourlifting motors and lifting propellers and one or more thrusting motorsand thrusting propellers, in conjunction with a wing 718.

Still further, while the UAV 712 illustrates a single wing 718 extendingacross the top of the UAV 712, in other implementations, additionalwings and/or different configurations of wings may be utilized. Forexample, in one implementation, a wing may extend horizontally fromeither side of the UAV 712. In another implementation, a front wing mayextend from either side of the front of the UAV 712 and a larger rearwing may extend from either side of the rear of the UAV 712.

FIG. 8 is a flow diagram illustrating an example order deliveryselection process 800, according to an implementation. This process, andeach process described herein, may be implemented by the architecturesdescribed herein or by other architectures. The process is illustratedas a collection of blocks in a logical flow graph. Some of the blocksrepresent operations that can be implemented in hardware, software, or acombination thereof. In the context of software, the blocks representcomputer-executable instructions stored on one or more computer readablemedia that, when executed by one or more processors, perform the recitedoperations. Generally, computer-executable instructions includeroutines, programs, objects, components, data structures, and the likethat perform particular functions or implement particular abstract datatypes.

The computer readable media may include non-transitory computer readablestorage media, which may include hard drives, floppy diskettes, opticaldisks, CD-ROMs, DVDs, read-only memories (ROMs), random access memories(RAMs), EPROMs, EEPROMs, flash memory, magnetic or optical cards,solid-state memory devices, or other types of storage media suitable forstoring electronic instructions. In addition, in some implementations,the computer readable media may include a transitory computer readablesignal (in compressed or uncompressed form). Examples of computerreadable signals, whether modulated using a carrier or not, include, butare not limited to, signals that a computer system hosting or running acomputer program can be configured to access, including signalsdownloaded through the Internet or other networks. Finally, the order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the process.

The example process 800 begins with the receipt of an order for an item,as in 802. Upon receiving an order for an item from a user, adetermination is made as to the estimated delivery timeframe for thatitem, as in 804. In some examples, this may include identifying amaterials handling facility and/or AFC with the requested item in stockand estimating the time required to fulfill the item to the user. Inother implementations, the estimated delivery timeframe may be a set dayfrom the date of the purchase request or a series of days. For example,a user may specify that the delivery timeframe is to be one day from thedate of the purchase request or between three and five days from thedate of the purchase request. In still other implementations, theestimated delivery timeframe may be a set day of the week upon which theuser has requested to have items delivered. For example, a user maypreselect to have items ordered during the week delivered on Thursday ofevery week. Alternatively, the estimated delivery timeframe may beimmediate delivery.

After the estimated delivery timeframe is determined, a determination ismade as to whether an AFC is or will be within a delivery area thatincludes a user specified delivery location, as in 806. As describedabove, in various implementations, AFCs may be positioned at fulfillmentcenter altitudes and UAVs may be deployed from the AFC to deliverordered items. Each AFC may have a corresponding delivery rangerepresentative of the range or distance a UAV can travel to deliver anitem when deployed from the AFC. In some implementations, a deliverylocation may be within the delivery range of multiple AFCs and/or groundbased materials handling facilities.

If it is determined that the delivery location is within the range ofone or more AFCs, a determination is made as to whether one of the AFCsis selected by the user for delivery, as in 808. In variousimplementations, an interaction may be received from a user through auser interface that presents delivery options to the user and receives aselection from the user (e.g., for selecting an AFC or other deliveryoption). In addition, in various implementations, a user may preselector provide a preference for deliveries from an AFC or other deliveryoptions.

In various implementations, different factors may be evaluated fordetermining whether an AFC will be presented as an option forfulfillment of an item. For example, an AFC's current and/or plannedinventory, available capacity, ability to handle items of certain sizes,suitability for delivering certain types of items via UAV (e.g., largeand/or heavy items), etc., may all be considered. If the user selects anavailable AFC, the selected AFC is designated for the delivery of theitem, as in 810.

If it is determined that an AFC is not selected for delivery, as in 808,or that no AFCs will be within the range of the delivery location, as in806, another type of delivery option is designated (e.g., as selected bythe user) for the item, as in 812. In various implementations, otherdelivery options may include traditional carrier deliveries, UAVdelivery from a materials handling facility, providing an item at apickup location where a user may retrieve the item, etc.

FIG. 9 is a flow diagram illustrating an example process 900 for adelivery of an item by a UAV deployed from an AFC, according to animplementation. The example process 900 begins with the UAV engaging theitem, as in 902. In various implementations, different types of UAVs mayhave different methods for engaging an item. For example, as describedabove with respect to FIG. 6, a UAV may include an inventory engagementmechanism for engaging an item. Likewise, in some implementations, theitem may be engaged by the UAV before it is ordered so that the UAV canbe deployed for delivery as soon as the item is ordered.

After the item is engaged, the UAV is deployed or otherwise releasedfrom the AFC and the UAV begins navigation along a delivery path towardthe specified delivery location using little or no power, as in 904. Asdiscussed above, as the UAV descends from the AFC, it may travel in apath that includes a horizontal component using little to no power bymanipulating the ailerons of a wing, if so equipped, and/or byselectively engaging the motors and corresponding propellers of the UAV.In various implementations, delivery path instructions may be receivedby the UAV (e.g., from the AFC, from the inventory management system,from a remote computing resource, etc.).

In some implementations, the UAV may also navigate to avoid any otheraircraft, such as commercial aircraft, private aircraft, and/or otherUAVs as it descends from the AFC. For example, the UAV may be providedwith flight path information of other aircraft and navigate to avoidintersections with those flight paths. In another example, the UAV maymonitor for ADS-B signals to detect and avoid nearby aircraft.

As the UAV descends, a determination is made as to whether the UAV hasentered the UAV network, as in 906. It may be determined that the UAVhas entered the UAV network when it is able to communicate with otherUAVs, join the UAV network discussed above with respect to FIGS. 2 and3, has reached a defined altitude, etc. If the UAV has not entered theUAV network, the example process 900 returns to block 904 and continues.Once it is determined that the UAV has entered the UAV network, the UAVmay engage the motors and corresponding propellers of the UAV to slowdescent of the UAV and to complete navigation of the UAV along thedelivery path to the delivery location, as in 909.

In some implementations, the UAV may receive additional information(e.g., weather) from UAVs of the UAV network and/or detect obstacles asit navigates toward the delivery location. As it receives informationand/or detects obstacles, the UAV may alter the delivery path that isfollowed to the delivery location. When the UAV arrives at the deliverylocation, the ordered item is disengaged from the UAV to complete thedelivery of the item, as in 910. After the UAV has disengaged the item,a confirmation of the delivery is sent from the UAV, as in 912. Invarious implementations, the confirmation of the delivery of the itemmay be received by the AFC, the inventory management system, a remotecomputing resource, other UAVs, etc., and may be utilized for updatingthe status in the inventory management system regarding the delivery ofthe item, planning inventory for the AFC, for providing a notificationto a user regarding the delivery, etc.

Once the confirmation of the delivery has been sent, a determination ismade as to whether the UAV will navigate to a shuttle for a trip back tothe AFC or another AFC, as in 914. If the UAV is to return to the AFC,the UAV receives return path instructions identifying a location of ashuttle replenishment location at which a shuttle is or will bepositioned that the UAV may utilize to travel upon back to the AFC.Accordingly, the UAV will navigate along the return path to the shuttlereplenishment location and land or otherwise be placed into a shuttlefor return to the AFC, as in 916. If the UAV is not to return to the AFCor another AFC, the UAV returns to another designated location, as in918. For example, the UAV may be instructed to navigate to a groundbased materials handling facility within the range of the UAV.

In various implementations, certain portions of the example process 900may be repeated, in particular with regard to deliveries of multipleitems. For example, if a UAV is carrying multiple items that are to bedelivered to different delivery locations, the UAV may travel from onedelivery location to another before navigating to a shuttle or anotherdesignated location.

The UAV item delivery process for delivering items using a UAV deployedfrom an AFC provides the ability for users to receive items quickly andwith limited transportation costs. For example, for items stocked ininventory at the AFC, the user may place an order for an item and havethe item delivered within ten minutes or less, in some examples.Likewise, through the use of UAVs, the items can be delivered tovirtually any user specified delivery location. For example, a user mayselect to have the item delivered directly to the location of the user.In such an example, location information may be determined and utilizedas the location of the user. For example, the GPS information of theuser's portable device may be utilized as the location of the user andthe item delivered to a location near the GPS position of the user'sportable device. If the user moves to a different location afterordering the item, the position of the user may be updated and the UAVmay update its navigation path based on the current location of theuser.

Likewise, with the speed of item delivery available from theimplementations discussed herein, a large variety of items may bedelivered to a user. In one example, the AFC may include a foodpreparation area and a user may order prepared food (such as a meal).The ordered food may be prepared, placed in a container and delivereddirectly to the user from the AFC using a UAV. The container may beconfigured to keep the food at the desired temperature (hot or cold)until delivery. Any other type of item that may be carried by a UAV maylikewise be delivered using the implementations discussed herein. Insome implementations, the AFC may be utilized to promote or advertiseitems and/or to fulfill an expected high demand at an area, such as alocation of a temporal event (e.g., sporting event, concert, or othergathering).

FIG. 10 is a flow diagram of an example airborne fulfillment centeradvertising and delivery process 1000, according to an implementation.The example process 1000 begins by navigating the AFC to an advertisingaltitude, as in 1002. Any altitude at which an advertisement can bereceived from an AFC may be utilized. For example, the advertisingaltitude may be approximately 2,000 feet. At such an advertisingaltitude, the AFC is not in the typical commercial flight altitude andis at an altitude so that the AFC is viewable by users located near theAFC.

Once the AFC is positioned at the advertising height, the advertisementis presented from the AFC, as in 1004. The advertisement may bepresented audibly, visually, and/or using other means. For example, aside portion of the AFC may include a display or a presentation devicethat can be used to visually present the advertisement. Alternatively,or in addition thereto, the AFC may include a speaker that can audiblyoutput the advertisement.

The advertisement may be for any type of item, whether it is deliverablefrom the AFC or otherwise. For example, the advertisement may be for aservice. In some implementations, the advertisement may relate to aquantity of items that are being sold for immediate delivery from theAFC. For example, the AFC may display an advertisement for an item andpresent a quantity of that item remaining that may be ordered forimmediate delivery from the AFC. Other examples include advertisementsfor pre-release items, sale items, consumable items, etc.

As the advertisement is presented, a determination is made as to whetheran order for the advertised item has been received, as in 1006. If it isdetermined that an order has not been received, the example process 1000proceeds to block 1010 and determines if the advertisement is tocontinue, as discussed below. If an order for the advertised item isreceived, the UAV item delivery process 900 (discussed above withrespect to FIG. 9) is performed and the item is delivered to the user.

As the item is delivered, the advertisement may be updated, as in 1008.For example, if the advertisement includes a quantity count for thenumber of items being sold as part of the advertisement, the quantityremaining may be updated to reflect the sold item.

A determination is also made as to whether the advertisement is tocontinue, as in 1010. For example, the advertisement may be scheduled tobe presented for a defined period of time, until a defined quantity ofthe advertised item has been sold, and/or based on other factors. If itis determined that the advertisement is to continue, the example process1000 returns to block 1004 and continues. However, if it is determinedthat the advertisement is not to continue (e.g., the time duration ofthe advertisement has expired, the quantity of items associated with theadvertisement have been sold, etc.), the AFC may terminate presentationof the advertisement and navigate from the advertising altitude, as in1012. For example, the AFC may navigate back up to the fulfillmentcenter altitude where the AFC was previously positioned, the AFC mayland, etc. After navigating from the advertising altitude, the exampleprocess 1000 completes, as in 1014.

Utilizing the AFC to advertise items for immediate delivery providesadditional flexibility in inventory management and item promotion. Forexample, if it is determined that an item is overstocked at the AFC,rather than sending the items to another location using a shuttle, theitems may be advertised at a reduced price to deplete the overstock ofinventory. Likewise, if the AFC is scheduled to land for service,restocking and/or for other purposes, as part of the descent towardlanding, the AFC may navigate to an advertisement altitude and advertisethe sale of one or more of the items currently in inventory of the AFC.

As inventory, UAVs, supplies, etc., are depleted from the AFC, and/orduring times of low activity, the AFC may descend and land.Alternatively, as discussed herein, shuttles may be utilized to deliverinbound items to the AFC so that the AFC can remain airborne forextended periods of time.

FIG. 11 is a flow diagram of an example shuttle process 1100, accordingto an implementation. The example process 1100 begins when a shuttle ispositioned on the ground at a shuttle replenishment location. A shuttlereplenishment location may be any designated location at which a shuttlemay be positioned.

As part of the example process 1100, inbound items that are to betransported to the AFC are loaded onto the shuttle, as in 1102. Inbounditems may be any item that is to be transported to the AFC. For example,inbound items may be inventory, UAV, workers, fuel, supplies,contractors, etc. In some implementations, as discussed above, a shuttlemay hold a variety of different types of inbound items. In otherimplementations, shuttles may be designed for one or more types ofinbound items. For example, some shuttles may be partially or entirelydesignated for UAV transport. Such shuttles may be configured withcharging stations to enable charging of UAVs during the transport fromthe shuttle replenishment location to the AFC. Likewise, tools and/orpersonnel necessary to service or repair UAVs may also be included onthe shuttle. In other examples, shuttles may be partially or entirelydesignated for inventory transport and/or people (e.g., workers)transport. For example, some shuttles may include seats, safetyequipment, etc., to ensure the safe transport of humans to and from theAFC.

As the shuttle is loaded with inbound items, a determination is made asto whether the shuttle is to depart for the AFC, as in 1104. Determiningwhether to depart for the AFC may be based on a variety of factorsincluding, but not limited to, the type of inbound items beingtransported, the capacity of the shuttle, the need for the inbound itemsat the AFC, etc. For example, if the shuttle is used to transportworkers to the AFC, the shuttle may be scheduled to depart the shuttlereplenishment location at a designated time. Once the designated time isreached, the shuttle may depart. In another example, if the shuttle istransporting inventory and/or fuel, the need for the loaded inventoryand/or the fuel at the AFC may be determined. If additional inventory,fuel and/or other items are in-route to the shuttle replenishmentlocation, the estimated time until arrival of the additional inbounditems may likewise be considered. Still further, the time until the nextshuttle departure may likewise be considered in determining whether theshuttle is to depart for the AFC.

If it is determined that the shuttle is not to depart for the AFC, theexample process 1100 returns to block 1102 and continues. If it isdetermined that the shuttle is to depart for the AFC, the shuttledeparts the shuttle replenishment location and navigates to the AFC, asin 1105. The shuttle may be manually navigated to the AFC by an operatorof the shuttle, navigated using automated controls and/or a combinationthereof. As the shuttle navigates to the AFC, inbound items may beserviced. For example, UAVs may be charged by the shuttle, servicedand/or repaired as they are transported to the AFC.

When the shuttle arrives at the AFC, it is secured to and docked withthe AFC, as in 1106. Securing and docking of the shuttle may beaccomplished in a variety of manners depending on the shape andconfiguration of the AFC and the UAV. For example, a docking arm mayextend from the AFC and/or the shuttle and mate the shuttle to the AFC,thereby securing the position of the shuttle with respect to the AFC andproviding a channel through which inbound items may be transported fromthe shuttle to the AFC. In other implementations, the AFC may include ahangar or other opening into which the shuttle may navigate and becomefully or partially enclosed within the AFC. As will be appreciated, anytype of docking techniques may be utilized with the implementationsdiscussed herein.

Upon docking and securing of the shuttle with the AFC, the inbound itemsare unloaded from the shuttle into the AFC, as in 1108. For example,inventory may be transported from the shuttle to a receiving location ofthe AFC where the items are inducted into inventory of the AFC and madeavailable for picking and delivery. Likewise, the UAVs may be moved fromthe shuttle to a UAV staging area within the AFC where they may beserviced, charged, etc., while awaiting deployment instructions. Workersor other humans may likewise disembark from the shuttle into the AFC.

Once the inbound items to be delivered to the AFC have been removed fromthe shuttle, a determination is made as to whether outbound items are tobe loaded onto the shuttle before the shuttle departs the AFC, as in1110. Outbound items are any items that can be carried by the shuttlethat are to be removed from the AFC. For example, outbound items mayinclude overstock inventory, inventory that is to be shipped to anotherAFC or a ground based materials handling facility (referred to herein astransship inventory), damaged items, waste, workers, etc.

If it is determined that outbound items are to be loaded onto the AFC,the outbound items are loaded, as in 1112. As with inbound items, insome implementations, the shuttles may be designed for particular typesof outbound items. For example, some shuttles may be configured toreceive waste, damaged items, overstocked items and/or transshipments,while other shuttles may only receive humans. In some implementations,the destination of the shuttle after it departs the AFC may beconsidered when determining whether to load outbound items. For example,in some implementations, the shuttle may navigate to multiple AFCsdelivering inbound items before the shuttle returns to earth. In such anexample, non-humans may be loaded onto the shuttle and/or humans thatare to be transported to another AFC may be loaded.

After the outbound items have been loaded, or if it is determined atblock 1110 that no outbound items are to be loaded, the shuttle undocksfrom the AFC and navigates to a next scheduled destination (e.g.,shuttle replenishment location, another AFC), as in 1114. In someimplementations, similar to determining when a shuttle is to depart ashuttle replenishment location, a similar determination may be made asto when/whether a shuttle is to depart the AFC.

FIG. 12 is a block diagram illustrating an example UAV control system1210 that may be utilized with any of the UAVs discussed herein, such asthe UAV 612 of FIG. 6 or the UAV 712 of FIG. 7. In various examples, theblock diagram may be illustrative of one or more aspects of the UAVcontrol system 1210 that may be used to implement the various systemsand methods discussed herein and/or to control operation of the UAV. Inthe illustrated implementation, the UAV control system 1210 includes oneor more processors 1202, coupled to a memory, e.g., a non-transitorycomputer readable storage medium 1220, via an input/output (I/O)interface 1211. The UAV control system 1210 may also include motorscontrollers 1204, such as electronic speed controls (ESCs), power supplymodules 1206 and/or a navigation system 1208. The UAV control system1210 further includes an inventory engagement controller 1213, a networkinterface 1216, and one or more input/output devices 1218.

In various implementations, the UAV control system 1210 may be auniprocessor system including one processor 1202, or a multiprocessorsystem including several processors 1202 (e.g., two, four, eight, oranother suitable number). The processor(s) 1202 may be any suitableprocessor capable of executing instructions. For example, in variousimplementations, the processor(s) 1202 may be general-purpose orembedded processors implementing any of a variety of instruction setarchitectures (ISAs), such as the x86, PowerPC, SPARC, or MIPS ISAs, orany other suitable ISA. In multiprocessor systems, each processor(s)1202 may commonly, but not necessarily, implement the same ISA.

The non-transitory computer readable storage medium 1220 may beconfigured to store executable instructions, data, flight paths, flightcontrol parameters, component adjustment information, center of gravityinformation, and/or data items accessible by the processor(s) 1202. Invarious implementations, the non-transitory computer readable storagemedium 1220 may be implemented using any suitable memory technology,such as static random access memory (SRAM), synchronous dynamic RAM(SDRAM), nonvolatile/Flash-type memory, or any other type of memory. Inthe illustrated implementation, program instructions and dataimplementing desired functions, such as those described herein, areshown stored within the non-transitory computer readable storage medium1220 as program instructions 1222, data storage 1224 and flight controls1226, respectively. In other implementations, program instructions, dataand/or flight controls may be received, sent or stored upon differenttypes of computer-accessible media, such as non-transitory media, onsimilar media separate from the non-transitory computer readable storagemedium 1220 or the UAV control system 1210. Generally speaking, anon-transitory, computer readable storage medium may include storagemedia or memory media such as magnetic or optical media, e.g., disk orCD/DVD-ROM, coupled to the UAV control system 1210 via the I/O interface1211. Program instructions and data stored via a non-transitory computerreadable medium may be transmitted by transmission media or signals suchas electrical, electromagnetic, or digital signals, which may beconveyed via a communication medium such as a network and/or a wirelesslink, such as may be implemented via the network interface 1216.

In one implementation, the I/O interface 1211 may be configured tocoordinate I/O traffic between the processor(s) 1202, the non-transitorycomputer readable storage medium 1220, and any peripheral devices, thenetwork interface or other peripheral interfaces, such as input/outputdevices 1218. In some implementations, the I/O interface 1211 mayperform any necessary protocol, timing or other data transformations toconvert data signals from one component (e.g., non-transitory computerreadable storage medium 1220) into a format suitable for use by anothercomponent (e.g., processor(s) 1202). In some implementations, the I/Ointerface 1211 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some implementations, the function of the I/Ointerface 1211 may be split into two or more separate components, suchas a north bridge and a south bridge, for example. Also, in someimplementations, some or all of the functionality of the I/O interface1211, such as an interface to the non-transitory computer readablestorage medium 1220, may be incorporated directly into the processor(s)1202.

The motor controllers 1204 communicate with the navigation system 1208and adjust the rotational speed of each lifting motor and/or thethrusting motor to stabilize the UAV and guide the UAV along adetermined flight path.

The navigation system 1208 may include a global positioning system(GPS), indoor positioning system (IPS), or other similar system and/orsensors that can be used to navigate the UAV to and/or from a location.The inventory engagement controller 1213 communicates with theactuator(s) or motor(s) (e.g., a servomotor) used to engage and/ordisengage items.

The network interface 1216 may be configured to allow data to beexchanged between the UAV control system 1210, other devices attached toa network, such as other computer systems (e.g., remote computingresources), and/or with UAV control systems of other UAVs. For example,the network interface 1216 may enable wireless communication between theUAV and a UAV control system that is implemented on one or more remotecomputing resources. For wireless communication, an antenna of a UAV orother communication components may be utilized. As another example, thenetwork interface 1216 may enable wireless communication betweennumerous UAVs. In various implementations, the network interface 1216may support communication via wireless general data networks, such as aWi-Fi network. For example, the network interface 1216 may supportcommunication via telecommunications networks, such as cellularcommunication networks, satellite networks, and the like.

Input/output devices 1218 may, in some implementations, include one ormore displays, imaging devices, thermal sensors, infrared sensors, timeof flight sensors, accelerometers, pressure sensors, weather sensors,etc. Multiple input/output devices 1218 may be present and controlled bythe UAV control system 1210. One or more of these sensors may beutilized to assist in landing as well as to avoid obstacles duringflight.

As shown in FIG. 12, the memory may include program instructions 1222,which may be configured to implement the example processes and orsub-processes described herein. The data storage 1224 may includevarious data stores for maintaining data items that may be provided fordetermining flight paths, landing, identifying locations for disengagingitems, etc. In various implementations, the parameter values and otherdata illustrated herein as being included in one or more data stores maybe combined with other information not described or may be partitioneddifferently into more, fewer, or different data structures. In someimplementations, data stores may be physically located in one memory ormay be distributed among two or more memories.

Those skilled in the art will appreciate that the UAV control system1210 is merely illustrative and is not intended to limit the scope ofthe present disclosure. In particular, the control system may includeany combination of hardware or software that can perform the indicatedfunctions. The UAV control system 1210 may also be connected to otherdevices that are not illustrated, or instead may operate as astand-alone system. In addition, the functionality provided by theillustrated components may, in some implementations, be combined infewer components or distributed in additional components. Similarly, insome implementations, the functionality of some of the illustratedcomponents may not be provided and/or other additional functionality maybe available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or storage while being used,these items or portions of them may be transferred between memory andother storage devices for purposes of memory management and dataintegrity. Alternatively, in other implementations, some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated UAV control system 1210. Some or all ofthe system components or data structures may also be stored (e.g., asinstructions or structured data) on a non-transitory,computer-accessible medium or a portable article to be read by anappropriate drive. In some implementations, instructions stored on acomputer-accessible medium separate from the UAV control system 1210 maybe transmitted to the UAV control system 1210 via transmission media orsignals such as electrical, electromagnetic, or digital signals,conveyed via a communication medium such as a wireless link. Variousimplementations may further include receiving, sending or storinginstructions and/or data implemented in accordance with the foregoingdescription upon a computer-accessible medium. Accordingly, thetechniques described herein may be practiced with other UAV controlsystem configurations.

FIG. 13 is a pictorial diagram of an illustrative implementation of aserver system 1320 that may be used in the implementations describedherein. The server system 1320 may include a processor 1300, such as oneor more redundant processors, a video display adapter 1302, a disk drive1304, an input/output interface 1306, a network interface 1308, and amemory 1312. The processor 1300, the video display adapter 1302, thedisk drive 1304, the input/output interface 1306, the network interface1308, and/or the memory 1312 may be communicatively coupled to eachother by a communication bus 1310.

The video display adapter 1302 provides display signals to a display(not shown in FIG. 13) permitting an agent of the server system 1320 tomonitor and configure operation of the server system 1320 and/or toprovide information (e.g., regarding transportation and/or storage of anitem by the AFC, shuttle and/or UAV). The input/output interface 1306likewise communicates with external input/output devices not shown inFIG. 13, such as a mouse, keyboard, scanner, or other input and outputdevices that can be operated by an agent of the server system 1320. Thenetwork interface 1308 includes hardware, software, or any combinationthereof, to communicate with other computing devices. For example, thenetwork interface 1308 may be configured to provide communicationsbetween the server system 1320 and other computing devices, such as thatof an AFC, materials handling facility, delivery location, UAV and/orshuttle, via a network.

The memory 1312 generally comprises random access memory (RAM),read-only memory (ROM), flash memory, and/or other volatile or permanentmemory. The memory 1312 is shown storing an operating system 1314 forcontrolling the operation of the server system 1320. A binaryinput/output system (BIOS) 1316 for controlling the low-level operationof the server system 1320 is also stored in the memory 1312.

The memory 1312 additionally stores program code and data for providingnetwork services to the AFC, shuttle, UAV, materials handling facility,and/or the inventory management system. The program instructions enablecommunication with a data store manager application 1321 to facilitatedata exchange between the data store 1309 and the inventory managementsystem.

As used herein, the term “data store” refers to any device orcombination of devices capable of storing, accessing, and retrievingdata, which may include any combination and number of data servers,databases, data storage devices and data storage media, in any standard,distributed or clustered environment. The server system 1320 can includeany appropriate hardware and software for integrating with the datastore 1309 as needed to execute aspects of one or more applications foran AFC, shuttle, materials handling facility, delivery location, UAV,and/or the inventory management system.

The data store 1309 can include several separate data tables, databasesor other data storage mechanisms and media for storing data relating toa particular aspect. For example, the illustrated data store 1309includes mechanisms for maintaining information related to operations,inventory, maps, GPS data, etc., which can be used to generate anddeliver information to an AFC, shuttle, UAV, and/or inventory managementsystem 1326. It should be understood that there might be additionalaspects that can be stored in the data store 1309 and that additionaldata stores beyond the one illustrated may be included. The data store1309 is operable, through logic associated therewith, to receiveinstructions from the server system 1320 and obtain, update or otherwiseprocess data in response thereto.

The memory 1312 may also include the inventory management system 1326,discussed above. The inventory management system 1326 may be executableby the processor 1300 to implement one or more of the functions of theserver system 1320. In one implementation, the inventory managementsystem 1326 may represent instructions embodied in one or more softwareprograms stored in the memory 1312. In another implementation, theinventory management system 1326 can represent hardware, softwareinstructions, or a combination thereof.

The server system 1320, in one implementation, is a distributedenvironment utilizing several computer systems and components that areinterconnected via communication links, using one or more computernetworks or direct connections. However, it will be appreciated by thoseof ordinary skill in the art that such a system could operate equallywell in a system having fewer or a greater number of components than areillustrated in FIG. 13. Thus, the depiction in FIG. 13 should be takenas being illustrative in nature and not limiting to the scope of thedisclosure.

Those skilled in the art will appreciate that in some implementationsthe functionality provided by the processes and systems discussed abovemay be provided in alternative ways, such as being split among moresoftware modules or routines or consolidated into fewer modules orroutines. Similarly, in some implementations, illustrated processes andsystems may provide more or less functionality than is described, suchas when other illustrated processes instead lack or include suchfunctionality respectively, or when the amount of functionality that isprovided is altered. In addition, while various operations may beillustrated as being performed in a particular manner (e.g., in serialor in parallel) and/or in a particular order, those skilled in the artwill appreciate that, in other implementations, the operations may beperformed in other orders and in other manners. Those skilled in the artwill also appreciate that the data structures discussed above may bestructured in different manners, such as by having a single datastructure split into multiple data structures or by having multiple datastructures consolidated into a single data structure. Similarly, in someimplementations, illustrated data structures may store more or lessinformation than is described, such as when other illustrated datastructures instead lack or include such information respectively, orwhen the amount or types of information that is stored is altered. Thevarious methods and systems as illustrated in the figures and describedherein represent example implementations. The methods and systems may beimplemented in software, hardware, or a combination thereof in otherimplementations. Similarly, the order of any method may be changed andvarious elements may be added, reordered, combined, omitted, modified,etc., in other implementations.

From the foregoing, it will be appreciated that, although specificimplementations have been described herein for purposes of illustration,various modifications may be made without deviating from the spirit andscope of the appended claims and the elements recited therein. Inaddition, while certain aspects are presented below in certain claimforms, the inventors contemplate the various aspects in any availableclaim form. For example, while only some aspects may currently berecited as being embodied in a computer readable storage medium, otheraspects may likewise be so embodied. Various modifications and changesmay be made as would be obvious to a person skilled in the art havingthe benefit of this disclosure. It is intended to embrace all suchmodifications and changes and, accordingly, the above description is tobe regarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A gas-filled aerial transport and deploymentsystem of unmanned aerial vehicles (UAVs), comprising: an airbornefulfillment center comprising: a lifting portion that includes a lighterthan air gas; and a fulfillment portion that is secured with the liftingportion such that the lifting portion lifts the fulfillment portion foraerial transport; wherein the fulfillment portion includes: a UAVstaging area configured to receive a plurality of UAVs staged to bedeployed to deliver items; and a UAV deployment bay that enables a UAVof the plurality of UAVs to be deployed while the airborne fulfillmentcenter is in flight and while the UAV is carrying an item to bedelivered to a delivery location that is within a delivery range of theairborne fulfillment center.
 2. The gas-filled aerial transport anddeployment system of UAVs of claim 1, wherein the UAV of the pluralityof UAVs includes: an antenna and a control system such that the controlsystem implements instructions received through the antenna to aeriallynavigate or deliver an item to the delivery location.
 3. The gas-filledaerial transport and deployment system of UAVs of claim 1, wherein theUAV of the plurality of UAVs includes: an antenna and a control systemsuch that the control system implements return path instructionsreceived through the antenna to aerially navigate to a shuttlereplenishment location after delivery of the item.
 4. The gas-filledaerial transport and deployment system of UAVs of claim 1, the UAV ofthe plurality of UAVs further including: an item engagement mechanismthat engages at least one item or container that contains an item priorto the UAV being deployed.
 5. A method of aerially transporting anddeploying an unmanned aerial vehicle (UAV), comprising: carrying aplurality of UAVs within a fulfillment portion of an airbornefulfillment center that includes a lifting portion that contains alighter than air gas; and deploying at least one of the plurality ofUAVs through a deployment bay while the airborne fulfillment center isin flight and while the UAV is carrying an item to be delivered to adelivery location that is within a delivery range of the airbornefulfillment center.
 6. The method of claim 5, further comprising: for atleast one of the plurality of UAVs, controlling, through a controlsystem of the UAV, a flight of the UAV in navigating a return path to ashuttle replenishment location.
 7. The method of claim 5, furthercomprising: retrieving at least one package from a storage area of thefulfillment portion; and attaching the at least one package with a UAVof the plurality of UAVs prior to the UAV being deployed.
 8. The methodof claim 5, wherein the at least one of the plurality of UAVs is coupledto an item and maintained in the fulfillment portion of the airbornefulfillment center prior to an order for the item.
 9. The method ofclaim 5, wherein deploying the at least one of the plurality of UAVsfurther includes: deploying the at least one of the plurality of UAVswithout activating a motor of the at least one of the plurality of UAVsuntil a time after the at least one of the plurality of UAVs has beendeployed.
 10. The method of claim 5, further comprising: determiningthat the at least one of the plurality of UAVs has completed a deliveryof the item; and instructing the at least one of the plurality of UAVsto aerially navigate to a location other than a current location of theairborne fulfillment center.
 11. The method of claim 5, furthercomprising: maintaining the airborne fulfillment center at a definedlocation and ready to deploy a UAV in response to receiving an order foran item.
 12. The method of claim 5, further comprising: receiving at theairborne fulfillment center and while the airborne fulfillment center isairborne, additional inventory items or additional UAVs.
 13. Anapparatus, comprising: a lifting portion that contains a lighter thanair gas; a fulfillment portion coupled to the lifting portion, thefulfillment portion storing inventory that is transportable from theapparatus while the apparatus is airborne; and wherein the fulfillmentportion includes: an aerial vehicle staging area configured to store aplurality of aerial vehicles to be deployed from the apparatus todeliver items to delivery destinations; and a deployment bay thatenables deployment of at least one aerial vehicle from the apparatuswhile the apparatus is airborne.
 14. The apparatus of claim 13, furthercomprising: a presentation component that outputs at least oneadvertisement, wherein the at least one advertisement corresponds to atleast one of an item available for delivery from the apparatus, aservice, a pre-release item, a consumable item, or a sale item.
 15. Theapparatus of claim 13, further comprising: a docking bay configured toreceive a shuttle and enable transfer of at least one of an inbound itemor an outbound item between the apparatus and the shuttle.
 16. Theapparatus of claim 13, wherein the fulfillment portion contains at leastone of: a mobile drive unit, a forklift, a shelf, a bin, a tote, a cart,or a trolley.
 17. The apparatus of claim 13, further comprising: atleast one cable that couples the lifting portion and the fulfillmentportion.
 18. The apparatus of claim 13, wherein the fulfillment portionis mounted directly to the lifting portion.
 19. The apparatus of claim13, further comprising: a computing system that maintains a currentinventory level of inventory stored in the fulfillment portion.
 20. Theapparatus of claim 13, further comprising: a radiation shield to protecta worker located on the apparatus from an exposure.